of a section (to add \testcolumn, \blank
etc. to work around no.2). Is there any?
(2)
Page/column breaking is odd in that the preferred breaking point seems to be
one entry too early, i.e. the last entry of one letter end up in the next
column and the previous column is one line too short
}{ \setupinitial[location=text, n=4] \placeinitial \input{ward}
\setupinitial[location=text, n=6] \placeinitial \input{knuth} }
\stopmixedcolumns
\stoptext
Admitedly this example has lots of lettrines. I added some \testcolumn to fix
that, but now some columns are not balanced (page 3)
\starttext
Dear all,
I am using \starthanging to implement dropcaps (with small pdf files). I use
this Inside mixedcolumns (2 columns).
I’d like to know if there is a better way than \testcolumn[N], N being the
number of lines of the dropcap, to prevent the location of dropcap being cut
between end
\dosetdirectpagereference{\currentregister:\v!section:#1}%
\fi
\registerparameter\c!command{#1}%
\endgroup
\blank[\v!samepage]%
\registerparameter\c!after
\par
\nobreak}
That (2) case can be fixed by a small change:
\testcolumn[3]\registerparameter\c!command{#1
to be implemented
on ConTeXt/Lua side. It requires adding 'checking' commands to proper
places.
Only ConTeXt knows the item tree, it can count number of item in every level
and then decide where placing the command is appropriate.
The \testpage or \testcolumn are not IMHO sufficient here. They cannot
Dear All,
the following MWE works fine, but when that 'First line' is uncommented, I
am getting 'Undefined control sequence' error in the console (ConTeXt -
2014.06.22).
\starttext
\startcolumns[n=2]
%First Line
\testcolumn[2]\input{tufte}
\stopcolumns
\stoptext
Any idea what is wrong here
\dosetdirectpagereference{\currentregister:\v!section:#1}%
\fi
\registerparameter\c!command{#1}%
\endgroup
\blank[\v!samepage]%
\registerparameter\c!after
\par
\nobreak}
That (2) case can be fixed by a small change:
\testcolumn[3]\registerparameter\c!command{#1}%
But when tested on this MWE, you can
Hi,
The second page of the following document has overlapping text in the
second column (this has been as minimal as I can get):
\setuphead[section][before={\testcolumn[4]},]
\starttext
\startmixedcolumns[align=right, balance=yes, grid=strut,]
\dorecurse{5}{
\startsection
\startitemize
={\testcolumn[3]},]
\defineitemgroup[Instructions][inbetween={\blank[.25em]},]
\starttext
\startmixedcolumns[
align=right,
balance=yes,
grid=strut,
]
\dorecurse{5}{
\startsection[title={Section},]
\startInstructions
\item{Preheat the oven to 400°F}\item{Put a few cups of salt in a
gratin
On 12/3/2013 4:40 PM, Hans Hagen wrote:
On 12/3/2013 3:10 PM, Lars Huttar wrote:
...
Thanks again for your work on this.
We're continually reevaluating whether we can use the beta or need to
stick with the stable version. At the moment, it looks like we'll be
sticking with the stable
On 11/28/2013 1:34 PM, Hans Hagen wrote:
That macro was never meant for mixed columns. I made a variant that
works ok in mixed columns which will be in the next beta.
\setuptolerance[verytolerant]
\starttext
\startmixedcolumns
\dorecurse{4}{\input ward \par}
\testcolumn[10
}{\input ward \par}
\testcolumn[10][-1pt] % 10 lines - 1pt slack
\dorecurse{2}{\input ward \par}
\stopmixedcolumns
\stoptext
Ok. It looks like the second parameter to \testcolumn is now required
(it didn't used to be).
i'll fix that
What does this slack value do? Does it mean
On 11/28/2013 1:34 PM, Hans Hagen wrote:
That macro was never meant for mixed columns. I made a variant that
works ok in mixed columns which will be in the next beta.
Excellent. I will give it a try.
I see a context-setup-win64 dated 2013-11-28 19:45. Is that beta? I may
wait for the next one
On 11/29/2013 12:26 PM, Lars Huttar (SIL gmail) wrote:
On 11/28/2013 1:34 PM, Hans Hagen wrote:
That macro was never meant for mixed columns. I made a variant that
works ok in mixed columns which will be in the next beta.
Excellent. I will give it a try.
I see a context-setup-win64 dated
we couldn't get column balancing
to work in columnsets).
However one thing we do miss from columnsets is the control over widows
orphans in two ways: \testcolumn, and \setupcolumnsetlines.
\testcolumn[n] allowed us to do a conditional column break, so when we
were about to start a new subsection
in two ways: \testcolumn, and \setupcolumnsetlines.
\testcolumn[n] allowed us to do a conditional column break, so
when we
were about to start a new subsection heading, we could prevent it
being
an orphan at the bottom of the column; and when starting a paragraph
with a hangaround graphic
On 11/22/2013 11:37 PM, Lars Huttar wrote:
On 11/22/2013 4:59 PM, Hans Hagen wrote:
On 11/20/2013 11:12 PM, Lars Huttar wrote:
On 11/20/2013 4:47 PM, Lars Huttar wrote:
However one thing we do miss from columnsets is the control over widows
orphans in two ways: \testcolumn
On 11/20/2013 11:12 PM, Lars Huttar wrote:
On 11/20/2013 4:47 PM, Lars Huttar wrote:
However one thing we do miss from columnsets is the control over widows
orphans in two ways: \testcolumn, and \setupcolumnsetlines.
\testcolumn[n] allowed us to do a conditional column break, so when we
were
On 11/22/2013 4:59 PM, Hans Hagen wrote:
On 11/20/2013 11:12 PM, Lars Huttar wrote:
On 11/20/2013 4:47 PM, Lars Huttar wrote:
However one thing we do miss from columnsets is the control over widows
orphans in two ways: \testcolumn, and \setupcolumnsetlines.
\testcolumn[n] allowed us to do
in columnsets).
However one thing we do miss from columnsets is the control over widows
orphans in two ways: \testcolumn, and \setupcolumnsetlines.
\testcolumn[n] allowed us to do a conditional column break, so when we
were about to start a new subsection heading, we could prevent it being
an orphan
On 11/20/2013 4:47 PM, Lars Huttar wrote:
However one thing we do miss from columnsets is the control over widows
orphans in two ways: \testcolumn, and \setupcolumnsetlines.
\testcolumn[n] allowed us to do a conditional column break, so when we
were about to start a new subsection heading, we
of a column and do a conditional \vskip based on that?(*)
- Avoid orphans: when starting a new section, if there's not enough room
left in the current column, do a column break before outputting the
section heading. I've tried \testcolumn[n], but it doesn't seem to work
right. What are the units
: when starting a new section, if there's not enough room
left in the current column, do a column break before outputting the
section heading. I've tried \testcolumn[n], but it doesn't seem to work
right. What are the units of the argument to \testcolumn?
We also do manual column balancing using
.
Is there a corresponding command to conditionally produce a column break?
Thanks,
Lars
I just looked at the implementation of \testpage in base/page-ini.tex
and found \testcolumn.
I imagine that should be analogous to \testpage, but hesitate to rely on
an undocumented feature, as it might be unused or obsolete code
.
Is there a corresponding command to conditionally produce a column break?
Thanks,
Lars
I just looked at the implementation of \testpage in base/page-ini.tex
and found \testcolumn.
I imagine that should be analogous to \testpage, but hesitate to rely on
an undocumented feature, as it might
}
\dorecurse{80}{dummy }
\startcolumns
\externalfigure[dummy][width=\textwidth]
\input tufte
\column
\column[preference] or \testcolumn[0]
\input tufte
\stopcolumns
\input tufte
\stoptext
Wolfgang
___
If your
can still insert a table.
\starttext
\section{first}
\dorecurse{80}{dummy }
\startcolumns
\externalfigure[dummy][width=\textwidth]
\input tufte
\column
\column[preference] or \testcolumn[0]
But I would need \column[verybigpreference] then. It doesn't make a
columnt break at all.
Mojca
think of any workaround :(
Well, in the worst case I can still insert a table.
\starttext
\section{first}
\dorecurse{80}{dummy }
\startcolumns
\externalfigure[dummy][width=\textwidth]
\input tufte
\column
\column[preference] or \testcolumn[0]
But I would need \column[verybigpreference
] or \testcolumn[0]
But I would need \column[verybigpreference] then. It doesn't make a
columnt break at all.
\installcolumnbreakhandler {MUL} \v!bigpreference
{\vfill\penalty-}
\unprotect
\installcolumnbreakhandler {MUL} \v!bigpreference
{\vfill\penalty-}
\protect
\startcolumns
]
\input tufte
\column
\column[preference] or \testcolumn[0]
But I would need \column[verybigpreference] then. It doesn't make a
columnt break at all.
\installcolumnbreakhandler {MUL} \v!bigpreference
{\vfill\penalty-}
\unprotect
\installcolumnbreakhandler {MUL} \v!bigpreference
30 matches
Mail list logo
